home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Gold Medal Software 4
/
Gold Medal Software - Volume 4 (Gold Medal) (1994).iso
/
netutils
/
novinst.arj
/
NOVINST
Wrap
Text File
|
1994-08-14
|
20KB
|
547 lines
*******************************************************************************
NOTE: The origin of this information may be internal or external to Novell. No
*******************************************************************************
NETWARE TCP/IP INSTALLATION AND CONFIGURATION ON A
NETWARE 3.11 FILESERVER
OCTOBER 1992
(This document DOES NOT include configuration of IP Tunnelling and Network Mana
ORGANIZATION OF THIS DOCUMENT
-----------------------------
I. PREREQUISITES FOR RUNNING TCP/IP
II. LOADING AND CONFIGURING NETWARE TCP/IP (as a TCP/IP node and a TCP/IP rout
III. POINTS TO CONSIDER WHEN CONFIGURING TCP/IP AS A NETWARE IP ROUTER
3.1 IP ROUTING BETWEEN DIFFERENT NETWORK SEGMENTS WITH THE NW311 ROUTER
3.2 SUBNETTING
3.3 SUBNET ZERO
3.4 CONFIGURING NETWARE TCP/IP WITH SUBNETS
EXAMPLE 1A
EXAMPLE 1B
EXAMPLE 1C
EXAMPLE 2
3.5 CLASS B AND C SUBNETS
IV. TESTING THE CONFIGURATION
STEP ONE
STEP TWO
STEP THREE
APPENDIX A - TOKEN RING SOURCE ROUTING
A.1 SOURCE ROUTING CONFIGURATION ON THE NETWARE FILESERVER
A.2 SOURCE ROUTING CONFIGURATION ON A WORKSTATION
APPENDIX B - INFORMATION TO PROVIDE WHEN PLACING A TECHNICAL SUPPORT CALL
I. PREREQUISITES
-----------------
* Computer - 80386- or 80486-based PC running NetWare 3.11 or higher
* RAM - At least 4MB
* LAN Adapter - Ethernet, Token-Ring or ARCNET adapter and corresponding driver
* LAN Driver - must be certified for NetWare 3.11
( Refer to page 2-1 of the "NetWare TCP/IP Transport Supervisor's Guide" for mo
II. LOADING AND CONFIGURING NETWARE TCP/IP
-------------------------------------------
NetWare TCP/IP comes standard with the NetWare 3.11 OS. NetWare TCP/IP does no
The installation of TCP/IP is accomplished when the NetWare OS is installed. I
1. Enter the following setting in the STARTUP.NCF file:
SET MAXIMUM PHYSICAL RECEIVE PACKET SIZE = 1514
This is discussed on page 259 of the "NetWare 3.11 System Administration Guide"
for Ethernet or ARCNET networks the setting should be 1514.
for Token-Ring networks the setting should be set to 4202.
(NOTE: If the fileserver is connecting an Ethernet or ARCNET network to a Token
Enter the following setting in the AUTOEXEC.NCF file:
SET MAXIMUM PACKET RECEIVE BUFFERS = 200
This is discussed on page 2-3 of the "NetWare TCP/IP Transport Supervisor's Gui
You can use MONITOR.NLM to observe the number of Packet Receive Buffers current
To get on-line help with the SET commands, at the NetWare console prompt enter
2. The LOAD TCPIP command usually located in the AUTOEXEC.NCF file, determines
To be seen as a TCP/IP host on the network, enter the command:
LOAD TCPIP
If the NetWare 3.11 fileserver is to route IP packets, the command would be:
LOAD TCPIP FORWARD=YES
Three options that can be specified with the LOAD TCPIP command:
LOAD TCPIP [FORWARD = {YES|NO}] [RIP = {YES|NO}] [TRAP = ip_address]
"FORWARD = YES" configures the server as an IP router; default is NO.
RIP enables or disables routing information protocol; default is YES.
TRAP specifies the IP address to which the local system should send SNMP
trap messages.
For more information, see pages 3-2 through 3-4 in the "NetWare v3.11 TCP/IP
3. Load the LAN driver.
For an Ethernet LAN driver:
LOAD lan-driver INT=int PORT=port FRAME=ETHERNET_II NAME=ip_enet
For a Token-Ring LAN driver:
LOAD lan-driver FRAME=TOKEN-RING_SNAP NAME=ip_token
For an ARCNET LAN driver:
LOAD lan-driver INT=int PORT=port FRAME=NOVELL_RX-NET NAME=ip_arc
NOTE: The "NAME" given at the end of each line is a unique name that you select
IP LOAD statement might have NAME=IP_LAN.
LOAD NE3200 INT=3 PORT=300 FRAME=ETHERNET_802.3 NAME=IPX_LAN
LOAD NE3200 INT=3 PORT=300 FRAME=ETHERNET_II NAME=IP_LAN
For more information refer to Chapter 3 of the "NetWare TCP/IP Transport Superv
4. Follow the above command with BIND command:
BIND IPX TO name NET=#
BIND IP TO name ADDR=#.#.#.# [MASK= subnet mask]
"NET" is the IPX network number.
"name" is the value assigned in the LOAD statement as the "NAME" parameter.
"ADDR" is the IP address to be assigned to this NIC.
"MASK" (optional) is used if a subnet is specified on the network.
"#" specifies a numerical value which can be in either decimal or hexidecimal,
The BIND command has several options which are explained in the "NetWare TCP/IP
An example of the BIND commands:
BIND IPX to IPX_LAN NET=2
BIND IP to IP_LAN ADDR=130.2.1.254 MASK=FF.FF.FF.0
An example of entries in the NetWare 3.11 AUTOEXEC.NCF file to provide routing
SET MAXIMUM PACKET RECEIVE BUFFERS = 200
LOAD TCPIP FORWARD=YES
LOAD NE3200 int=3 port=300 frame=ETHERNET_802.3 name=IPX_LAN
LOAD NE3200 int=3 port=300 frame=ETHERNET_II name=IP_LAN
LOAD TOKEN frame=ETHERNET_802.3 name=IPX_TOKEN
LOAD TOKEN frame=TOKEN-RING_SNAP name=IP_TOKEN
LOAD SMCPLUSSV int=5 port=320 frame=NOVELL_RX-NET NAME=ARCNET
BIND IPX to IPX_LAN net=1
BIND IP to IP_LAN addr=130.2.1.254 mask=FF.FF.FF.0
BIND IPX to IPX_TOKEN net=2
BIND IP to IP_TOKEN addr=130.2.2.254 mask=FF.FF.FF.0
BIND IPX to ARCNET net=3
BIND IP to ARCNET addr=130.2.3.254 mask=255.255.255.0
For additional sample IP network configurations, refer to Chapter 5 of the "Net
In the above example note that there is only one LOAD statement for ARCNET. Fo
NOTE: If all of the servers on the network are NetWare 3.11, Ethernet NICs may
III. POINTS TO CONSIDER WHEN CONFIGURING TCP/IP AS A NETWARE IP ROUTER
-----------------------------------------------------------------------
IP addresses are differentiated into three classes based on the two most signif
An IP address consists of two parts, the network address and the host address.
"n"=network address, "h"=host address
Class A 0nnnnnnn.hhhhhhhh.hhhhhhhh.hhhhhhhh 7 bits of network address, 24 bits
Class B 10nnnnnn.nnnnnnnn.hhhhhhhh.hhhhhhhh 14 bits of network address, 16 bit
Class C 110nnnnn.nnnnnnnn.nnnnnnnn.hhhhhhhh 21 bits of network address, 8 bits
Where the first byte of an IP address fits in ranges listed below, tells you to
Class A - 1 to 127 (Class A: 1.h.h.h - 127.h.h.h).
Class B - 128 to 191 (Class B: 128.n.h.h - 191.n.h.h).
Class C - 192 to 223 (Class C: 192.n.n.h - 223.n.n.h).
An IP address beginning with 154 would be a Class B address, with the first two
(Refer to pages B-7 through B-9 of the "NetWare TCP/IP Transport Supervisor's G
The network portion of an IP address should be the same for all nodes that belo
3.1 IP ROUTING BETWEEN DIFFERENT NETWORK SEGMENTS WITH THE NW311 ROUTER
------------------------------------------------------------------------
Routing packets is done between different physical networks. When the NetWare
Each board in the NetWare 3.11 fileserver needs to have a different IP network
3.2 SUBNETTING
---------------
In the "NetWare TCP/IP Transport Supervisor's Guide" on pages B-18 and B-19 the
to use multiple media
to reduce congestion
to reduce CPU use
to isolate a network
to improve security.
If an organization has been assigned a single IP network address, then they mus
For more information regarding methods of partitioning your network refer to pa
With subnetting, IP addresses may be interpreted as:
<net><subnet><host>
The <net> part is defined by the IP network address and the <subnet> and <host>
For example, a company has been assigned the Class B IP network number of 154.4
The following diagram gives the binary and decimal representation of the 3rd by
BINARY VALUE (subnet mask) - | 1 1 1 1 | | 1 1 1 1 |
BINARY VALUE (subnet mask) - | n n n n | | n n n n |
(n = network, h = host portion)
DECIMAL VALUE (for each bit) - | 128 64 32 16 | | 8 4 2 1 |
---------------- ------------
For more information on creating a subnet and the characteristics of a subnet r
3.3 SUBNET ZERO
----------------
A subnet of all zeros is not recommended by RFC 950 and is not supported by Nov
The subnet field must not contain all zeros; this is not supported and should n
3.4 CONFIGURING NETWARE TCP/IP WITH SUBNETS
--------------------------------------------
If no subnet mask is assigned, the subnet mask is the default IP network mask a
Class A IP addressing is 1 to 127 and has a default subnet mask of 255.0.0.0 (
Class B IP addressing is 128 to 191 and has a default subnet mask of 255.255.0
Class C IP addressing is 192 to 223 and has a default subnet mask of 255.255.2
If it is determined that subnet masking needs to be configured on the network,
BIND IP TO lan-driver ADDR=#.#.#.# MASK= #.#.#.#
(NOTE: The subnet mask can be assigned using either hexadecimal values of 0 thr
decimal values of 0 through 255. For example, the values of "FF.FF.0.0" and "
In assigning the subnet mask, make the subnet bits contiguous and located as th
For example, the binary representation of a subnet mask of 255.255.49.0 (FF.FF.
|1111 1111| |1111 1111| |0011 0001| |0000 0000|
----------- ----------- ----------- -----------
By having the bits of the subnet mask non-contiguous and not located as the mos
A more desirable approach is to use a subnet mask of 255.255.224.0 (FF.FF.E0.0)
|1111 1111| |1111 1111| |1110 0000| |0000 0000|
----------- ----------- ----------- -----------
The simpest method of subnet masking is to mask off an entire byte, as describe
EXAMPLE 1
---------
For this example we are using the Class C IP address of 192.1.1.0 which has a d
192.1.1.0 (neither the 8th or 7th bits are turned on) ... subnet zero
192.1.1.64 (7th bit of 4th byte turned on)
192.1.1.128 (8th bit of 4th byte turned on)
192.1.1.192 (8th and 7th bits of 4th byte turned on) ... subnet all ones
Therefore a subnet mask of 255.255.255.192 (FF.FF.FF.C0) would provide two vali
*******************************************************************************
NOTE: It is recommended by RFC 950 that the values of all zeros, and all ones i
*******************************************************************************
EXAMPLE 1-A
-----------
The fourth byte of the IP address on the network 192.1.1.128, with the subnet m
BINARY VALUE (subnet mask) - | 1 1 0 0 | | 0 0 0 0 |
BINARY VALUE (subnet mask) - | n n h h | | h h h h |
(n = network, h = host portion)
BINARY VALUE (network #.#.#.128) | 1 0 0 0 | | 0 0 0 0 |
BINARY VALUE (IP addr #.#.#.139)| 1 0 0 0 | | 1 0 1 1 |
DECIMAL VALUE (for each bit) - | 128 64 32 16 | | 8 4 2 1 |
---------------- -------------
NOTE: The value of "64" can not be used in determining the IP address of the f
EXAMPLE 1-B
-----------
The fourth byte of the IP address on the network 192.1.1.64, with the subnet ma
BINARY VALUE (subnet mask) - | 1 1 0 0 | | 0 0 0 0 |
BINARY VALUE (subnet mask) - | n n h h | | h h h h |
(n = network, h = host portion)
BINARY VALUE (network #.#.#.64) | 0 1 0 0 | | 0 0 0 0 |
BINARY VALUE (IP addr #.#.#.116)| 0 1 1 1 | | 0 1 0 0 |
DECIMAL VALUE (for each bit) - | 128 64 32 16 | | 8 4 2 1 |
---------------- -------------
NOTE: The value of "128" can not be used in determining the IP address of the
EXAMPLE 1-C
-----------
The BIND statements for two cards in a NetWare fileserver could be:
BIND IP to IPNET1 ADDR=192.1.1.139 MASK=255.255.255.192
BIND IP to IPNET2 ADDR=192.1.1.116 MASK=255.255.255.192
NOTE: The IP network addresses of 192.1.1.128 and 192.1.1.64 (with the subnet
BIND IP to IPNET1 ADDR=192.1.1.128 MASK=255.255.255.192 (ILLEGAL ADDRESS
BIND IP to IPNET2 ADDR=192.1.1.64 MASK=255.255.255.192 (ILLEGAL ADDRESS
EXAMPLE 2
---------
For this example we are using the Class C IP address of 192.1.1.0 which has a d
192.1.1.0 (neither the 6th,7th or 8th bits are turned on) .... subnet
192.1.1.32 (6th bit, of 4th byte turned on)
192.1.1.64 (7th bit, of 4th byte turned on)
192.1.1.128 (8th bit, of 4th byte turned on)
192.1.1.96 (6th and 7th bits, of 4th byte turned on)
192.1.1.160 (6th and 8th bits, of 4th byte turned on)
192.1.1.192 (7th and 8th bits, of 4th byte turned on)
192.1.1.224 (6th, 7th and 8th bits, of 4th byte turned on) ... sub
When masking off the first three bits in the last byte (with the subnet mask of
192.1.1.32
192.1.1.64
192.1.1.96
192.1.1.128
192.1.1.160
192.1.1.192
The following diagram gives the binary and decimal representation of the 4th by
BINARY VALUE (subnet mask) - | 1 1 1 0 | | 0 0 0 0 |
BINARY VALUE (subnet mask) - | n n n h | | h h h h |
(n = network, h = host portion)
DECIMAL VALUE (for each bit) - | 128 64 32 16 | | 8 4 2 1 |
---------------- -------------
3.5 CLASS B and C SUBNETS
--------------------------
Possible Class C subnets:
BITS SUBNET MASK # of SUBNETS # of HOSTS
(recommended)
2 255.255.255.192 2 62
3 255.255.255.224 6 30
4 255.255.255.240 14 14
5 255.255.255.248 30 6
6 255.255.255.252 62 2
Possible Class B subnets:
2 255.255.192.0 2 16382
3 255.255.224.0 6 8190
4 255.255.240.0 14 4094
5 255.255.248.0 30 2046
6 255.255.252.0 62 1022
7 255.255.254.0 126 510
8 255.255.255.0 254 254
9 255.255.255.128 510 126
10 255.255.255.192 1022 62
11 255.255.255.224 2046 30
12 255.255.255.240 4094 14
13 255.255.255.248 8190 6
14 255.255.255.252 16382 2
For more information on subnet masking, read pages B-18 through B-22 in the "No
IV. TESTING THE NETWARE TCP/IP CONFIGURATION
---------------------------------------------
For purposes of illustration, assume that the network configuration we are goin
LWPD - 191.1.1.45 subnet mask 255.255.255.224 (IP network 191.1.1.32)
NW3.11 (board 1) - 191.1.1.60 subnet mask 255.255.255.224 (IP network 191.
NW3.11 (board 2) - 191.1.1.140 subnet mask 255.255.255.192 (IP network 191.1
UNIX - 191.1.1.137 subnet mask 255.255.255.192 (IP network 191.1.1.128)
LWPD NW3.11 fileserver UNIX host
---------------------- ---------------------- ----------------------
| | | <- 191.1.1.60 | | |
| 191.1.1.45 -> |---| (255.255.255.224) | | <- 191.1.1.137 |
| (255.255.255.224) | | |---| (255.255.255.192) |
---------------------- | 191.1.1.140 -> | ----------------------
| (255.255.255.192) |
----------------------
Once the IP addressing has been configured, you are ready to test the configura
STEP ONE
--------
To test the IP connection between the workstation and the fileserver, enter the
ping 191.1.1.60
If the response that is returned is "191.1.1.60 is alive", the IP packet was su
If you do not receive the confirmation that the IP packet was returned correctl
Things to check include:
(1) that the network portion of the IP addresses on both the workstation an
(2) the workstation and the fileserver use the same subnet mask (which coul
(3) the physical connection between the two hosts exists and is good.
STEP TWO
--------------
The next step in the testing process is to ping from the LWPD workstation, thro
ping 191.1.1.140
If the test is not successful:
(1) Verify that AUTOEXEC.NCF on the server contains the command "LOAD TCP
(2) Verify that the LWPD workstation has the entries "IP_ROUTER 191.1.1.6
(3) Verify the TCP/IP configuration on the fileserver by entering "CONFIG"
(4) If you are not able to resolve the problem you may want to contact you
Once you are successfully able to ping the second board in the fileserver, the
STEP THREE
----------
The final step in testing the configuration, is to ping from the LWPD workstati
ping 191.1.1.137
If the test is not successful:
(1) Ping from the UNIX host to the NetWare fileserver: "ping 191.1.1.140".
(2) Check the addressing on the fileserver, verifying that the correct net
(3) Ping from the UNIX host to the board in the fileserver that is attache
(4) Verify that the routing is configured correctly on the UNIX host by ma
On a UNIX system, the general command is:
ROUTE ADD <destination network> <gateway address> <metric>
For the UNIX host you are working with, check the manual pages for the exact sy
In this example, the command would be:
ROUTE ADD 191.1.1.32 191.1.1.140 1
This route command says that if there is a packet that is to be routed to netwo
To assign the NetWare server (IP address of 191.1.1.140) as the default router
ROUTE ADD 0.0.0.0 191.1.1.140 1
If there are other non-NetWare TCP/IP routers on the network, verify that those
NOTE: If routing is configured correctly on one network but not on the other,
After the above steps have been completed, and routing has been configured corr
APPENDIX A - TOKEN RING SOURCE ROUTING
----------------------------------------
A.1 - SOURCE ROUTING CONFIGURATION on the NETWARE FILESERVER
--------------------------------------------------------------
To route IP packets through IBM source routing bridges you need to enter the fo
LOAD ROUTE BOARD=01
LOAD ROUTE BOARD=02
NOTE: These LOAD statements need to be entered in the AUTOEXEC.NCF file after t
ALSO NOTE: The board numbers listed in the load statements are logical boards.
To determine the value to assign to the "LOAD ROUTE BOARD=#" command:
- at the NetWare console prompt enter LOAD TCPCON
- then select <INTERFACE TABLE>
Locate the entry(ies) for the Token Ring LAN driver and note the logical board
For more information refer to the "NetWare 3.11 System Administration" guide on
A.2 - SOURCE ROUTING CONFIGURATION ON A WORKSTATION
-------- ------------------------------------------
If you are using source routing on a LWPD workstation, specify the following co
LSL
LANSUP (or TOKEN)
IPXODI
ROUTE BOARD=1
ROUTE BOARD=2
NETX
The ROUTE.COM is loaded twice because both frame types (IPX and IP) require sou
NOTE: The values for the ROUTE.COM command in the AUTOEXEC.BAT file are determi
For more information refer to the "NetWare ODI Shell for DOS" guide, on pages 3
APPENDIX B - INFORMATION TO PROVIDE WHEN PLACING A TECHNICAL SUPPORT CALL
---------------------------------------------------------------------------
When calling your Novell Reseller, Novell Technical Support or posting a NetWir
- The IP address of your local host.
- The IP address of a remote host.
- The IP addresses of the two (or more) interface cards in the NetWare 3.11 f
- The subnet mask for both the local and remote networks.
- Information from the NET.CFG (LWPD) file.
- Information from the AUTOEXEC.NCF (NetWare 3.11 fileserver) file.
- Information from the NetWare console command "CONFIG".
- Test results from the "ping" command (from the tests outlined in section IV
- "root" access to any UNIX systems that might be involved in the configurati
- "SUPERVISOR" access to the NetWare fileserver.
To receive technical support, contact your local Novell Reseller and request su
For support on NetWire, post questions in NOVA section 8 (NetWare NFS/TCP). (I
To place a call with Novell Technical Support call 800-NETWARE (800-638-9273) o